The Ejb connector allows Ejb session beans to be invoked as part of an event flow. Components can be given an ejb outbound endpoint which will invoke the remote object and optionally return a result.

The javadoc for this transport provider can be found here. And the Source Xref can be found here.

Ejb Connector Properties

For example -

<connector name="ejbConnector" className="org.mule.providers.ejb.EjbConnector">
    <properties>
        <property name="securityPolicy" value="wideopen.policy"/>
    </properties>
</connector>

Endpoints

Rmi endpoints are described as socket-based endpoints in the form of -

ejb://localhost:1099/[remote home name]?method=[method to invoke]

Using Rmi Connector

Note that only outbound endpoints can use the Ebj transport.

For a given endpoint, the following informationwill have to be written in the uri (uri path and parameter) :

• registry host
• registry port
• romote home name
• remote method name

these values will be used to establish dispatcher connection.

<endpoint address="ejb://localhost:1099/SomeService?method=remoteMethod">

If the remoteMethod can take 1 or more input arguments then they should be configured on the endpoint as list properties.

<properties>
    <list name="methodArgumentTypes">
        <entry value="java.lang.String"/>
        <entry value="java.lang.String"/>
    </list>
</properties>

Multiple arguments are passed in as an array of objects as the payload of the Mule event.

Transformers

There are no specific transformers required for Ejb.